Night Owl 6/Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso/049a/jet110b7.zip/JET110.NEW

Text File | 1992-01-05 | 10KB | 205 lines

BETA!! │ JetMail v1.10ß6 (c)Copyright 1991 by DJ Chuang
       │ .QWK-Compatible Mail Door for SPITFIRE 3.x

IMPORTANT REVISION! VERSION 1.10

1 - New way of doing Transfer Protocols.  Be sure to put JETXFER.DAT in
    your JetMail directory, and check its contents for use on your
    system. (details under 1.10ß1 changes)
2 - JetMail uses a new text file for its internal messages/prompts:
    JETTEXT.DAT now replaces JETMAIL.ERR.  Be sure to use the new .DAT
    file include with 1.10ß3 and later.

Version 1.10ß7 Changes (01/05/92)
  -  Compiled with new CKIT toolkit (2.10), which allows for byte
     alignment in the code. Don't know if this will clear up the memory
     problem that are on a few systems, which I can't duplicate, thus
     unable to track down.
  -  Rearranged message pointers reading algorithm, so JetMail doesn't
     take as long to initialize upon opening. This should be a
     considerable and noticeable time saver.
  -  Removed SERIAL parameter from JetMail .CNF configuration; most (if
     not all?) readers ignore this field now.
  -  Added PRIORITY= parameter to JetMail .CNF configuration. Set
     PRIORITY=YES to override Spitfire's security level check, if you as
     sysop would like to have to conferences that allow access only to a
     specific user security level. Defaults to NO. For example, with
     sysop security level set to 100, if a conference is for security
     level 10 only, some sysops don't want access to the conference
     either. But some sysops do (without giving access to sec levels
     between 10 and 100, which would open the conference to non-sysops).
     This parameter may be toggled accordingly.
  -  Builds NETFLAGS.DAT file for NetSysop packets. This file specifies
     precisely in which conferences a node sysop has NetSysop access.
  -  Places an ascii 0 in the message headers for 'extended' conference,
     indicating that conferences are numbered from 1 to 255.
     (compatibility adjustment for some QWK readers/networkers)

Version 1.10ß6 Changes (12/06/91)
  -  Touched up code to attempt to relieve problem of transfer protocol
     not getting called after initial QWK packet is built.
  -  Added .CNF parameter AFTER=to specify command line to call after an
     .REP upload, in case you'd like to call a dupe checker like KQDUP
     by Cody Gibson. Sample command line for using this utility:

     AFTER=KILLQ.EXE D:\TMP\ROCK.MSG -CF:C:\JM\ROCK.CRC -Log:C:\JM\KQDUP.LOG

     Note above sample .CNF is for a BBSID=ROCK, and WORKDIR=D:\TMP ,
     with JetMail home directory of C:\JM\ . Enter this into your DOS
     environment before calling JetMail, or in your AUTOEXEC.BAT:
     SET KILLQDUP=-DN:JETMAIL -MC:8000 -MD:14 -Com:1
     These are switch settings for KILLQ. Check KQDUP documentation for
     customizing these switches.

Version 1.10ß5 Changes (11/25/91)

  -  Added %D% parameter to JETXFER.DAT command line, which will be
     replaced with the drive & path to the JetMail work directory. This
     is needed by HS/Link and TModem for receiving files (and any other
     protocols that require only pathname and NOT filename when
     receiving files). Note new sample HS/Link command lines in
     JETXFER.DAT included with this ZIP.

  -  Properly parses multi-line file descriptions during New Files Scan,
     when secondary lines are delimited by chr(2).

Version 1.10ß4 Changes (11/16/91)

  -  Added HS/Link support, a new bi-directional protocol by Samuel
     Smith. JetMail will sense the upload of an .REP packet in the
     JetMail work directory and process it, if a user has uploaded an
     .REP while downloading a .QWK. (that's what bi-directional transfer
     is all about anyways, right?) So now the user can download a .QWK
     while uploading an .REP reply packet. Should save time! Refer to
     JETXFER.DAT for sample transfer command line setup.

  -  Added date timestamp in JetMail caller log if you're using the LOG=
     switch to use a separate log file for the JetMail door (instead of
     having all JetMail activity recorded to Spitfire's CALLERS.LOG)

  -  No longer says "Logoff due to Carrier Lost." if user is
     auto-logoff'ing or Goodbye'ing from JetMail.

  -  JetMail menus are now displayed continuously - it won't get
     interrupted by a 'More:' prompt if you have a fancy ANSI menu.

Version 1.10ß3 Changes (10/24/91)

  -  Sorry, a bad switch snuck into the beta 2 compilation which messed
     up the upload replies processing.  Fixed.

Version 1.10ß2 Changes (10/24/91)

  -  Updated JetMail's internal messages data file.  Place JETTEXT.DAT
     in your JetMail directory, and you may delete JETMAIL.ERR.
  -  Added code to make sure to tell user to go to configuration
     setup when transfer protocol was not selected.
  -  Streamlined code a little bit for handling transfer protocols and
     memory management.
  -  Fixed code to restore screen properly after file transfer.

Version 1.10ß1 Changes (10/20/91)

  -  It has been a busy weekend as portions of JetMail are re-done; I am
     also working on sprucing up JETSM so that you can do all of your
     JetMail configuration and setup within that program, but that will
     take more time, so I've decided to go ahead and let the JETMAIL.EXE
     out by itself first.

  *  MAKE A BACKUP OF YOUR JETMAIL HOME DIRECTORY BEFORE UPGRADING!

  -  Please let your users know that file transfers are done
     differently!  They may need to change their transfer protocol
     letter.

  -  Major Update: Internalized file transfer routines.  I know how
     confusing JetMail file transfers have been, and perhaps you're just
     getting settled in with having gotten file transfers to work; and
     now I go and change it.  I believe the changes will allow easier
     configuration, allow JetMail to run more efficiently, and also save
     you some bytes on the disk.

     You must place the JETXFER.DAT in your JetMail home directory, and
     have DSZ.COM (or equivalent) in your DOS path.  The format for this
     .DAT file is fairly simple:
        <L> Name_of_Protocol
        command_line_for_SEND_QWK_packet
        command_line_for_RECEIVE_QWK_packet

     You may add more protocols in the .DAT file accordingly, by adding
     three lines as above format.  Place the letter of the protocol
     between the brackets < >, and basically follow the example
     JETXFER.DAT included with this .ZIP.

     The first item in the command line must be a .COM or .EXE program,
     with the extension explicitly specified.

     The command line may have three macro-parameters specified (must be
     uppercase):
        %B%   baud rate (according to SPEED= setting in .CNF)
        %P%   port number
        %F%   filename to transfer

     When JetMail is ready to transfer a file (either to send a .QWK or
     to receive an .REP), it will automatically replace the above macros
     with the correct information.  After calling the transfer protocol
     engine, JetMail is able to detect the error level returned, and act
     accordingly.  JetMail expects the protocol engine to return with
     exit code 0 upon successful transfer, and exit code 1 (or greater)
     upon unsuccessful transfer.

     (After successful installation, you may delete the old JETDN/JETUP
     batch files, JETXFER.LST, and lingering XFER_ERR.JET.)

  -  Fixed approximate transfer time calcuation (there was a gross
     miscalculation introduced in recent code).

  -  Fixed problem when maximum number of messages in a conference is
     reached.  If messages are numbered from 100 to 500, and the message
     pointer was at 250, and the max. msgs. per conf. was set to 200,
     the old code would scan up to message 450 into the .QWK packet, but
     moved the message pointer to 500 after the transfer.  It now
     correctly sets the pointer to 450.  Plus, JetMail now prints an
     extra notice "Maximum message limit reached" for scripting.

  -  Removed kludge for processing NetSysop status users, when JetMail
     is used as a network hub.  Nodes may upload .REP's first, then
     download .QWK packet without risking downloading his own node's
     messages. (untested - please report your findings)

  -  Skip scanning CD-ROM file directories during new files scan.

Version 1.06ß6 Changes (10/17/91)
  -  Finally!  Found the elusive bug that was causing JetMail to
     generate garbled packets. [tech note: used text mode instead of
     binary mode, which resulted erroneous conference 13 messages].
     Thanks Paul Staton and Steve Newman.
  -  Sped up new files scan by scanning only SFFILES.BBS texts that have
     a newer file date than last file scan date.

Version 1.06ß5 Changes (10/13/91)

  -  JetMail now remembers the Expert Mode flag toggle from previous
     sessions. (toggle on Expert Mode once, and you'll never see the
     menu again in future logins)
  -  Removed code for special "PORT:" support (it was locking up)
  -  Added extra second when lowering DTR, when user selects Goodbye
     (if available) in JetMail {there's a NOBYE switch in the .CNF to
     let the sysop disable the Goodbye command in JetMail)
  -  Re-coded file size and date check; no longer conflicts with TSR
     utilities (like THELP).  There's something strange with using TC's
     stat() function with CKIT and THELP.
  -  Fixed one aspect of threading; if replying to an 'original'
     message, JetMail will now toggle that original message as the start
     of a thread, so when following a thread in Spitfire, it will be
     able to find start of thread now.  (Thanks Bob Zimmerman; this
     problem report was confusing to me, esp. since I setup a Spitfire
     3.0 where threading wasn't responding properly; now I've got
     Spitfire 3.1 setup for testing)


DJ Chuang, JetMail author
[phone] voice